Executive Summary

Video, rewritten as a programmable data layer

ION's video virtualisation architecture transforms rendered video from static, file-bound media into an addressable, time-indexed, orchestratable data layer that intelligent systems can assemble, personalise, and deliver progressively in real time, without re-encoding or duplicating source media.

Traditional video infrastructure treats compressed media as monolithic assets. Even within ISO Base Media containers where samples are technically indexed, the assembly map is static, generated once at encode time, binding structure, sequencing, and timing permanently to a single playback experience.

ION generalises and externalises this assembly layer.

Rather than treating the MP4 container as the final authority of structure, ION virtualises encoded video samples into a programmable reference space. Each compressed frame or segment becomes independently addressable, with timing, ordering, and inclusion controlled dynamically by an orchestration engine rather than a fixed sample table.

Architecture

How the architecture works

Programmable assembly

This enables intelligent systems to construct video experiences on demand. AI models can select, sequence, and time video components in real time based on user context, intent, behavioural signals, or inference outputs. Instead of rendering new video files, the orchestration layer computes a personalised assembly graph that maps virtualised references to underlying encoded media.

Progressive delivery

Progressive delivery occurs as the assembly is resolved. The system can begin streaming immediately while subsequent segments are dynamically selected and scheduled, enabling real-time personalisation, adaptive narratives, contextual highlights, summaries, and AI-driven content composition without re-encoding or duplicating media.

Decoupled infrastructure layers

From a systems perspective, ION decouples the following into independent, programmable layers:

• Encoded media storage
• Structural assembly
• Temporal orchestration
• Delivery sequencing

This collapses rendering pipelines, eliminates exponential storage growth, and enables AI-native interaction with video as a composable data substrate rather than a static asset.

Technical Foundation

How ISO Base Media functions as an assembly framework

Understanding ION requires understanding what MP4 and ISO Base Media Format actually are. They are not simply file formats. They are time-indexed assembly frameworks for compressed media.

The encoding pipeline

When a modern video encoder runs — whether H.264, HEVC, AV1, or similar — it does not create a movie file. It produces a continuous stream of compressed data units. Each unit represents the information needed to reconstruct a single moment in time. These units are called samples.

In almost all modern video workflows, one sample corresponds directly to one frame of video. Frame one becomes sample one, frame two becomes sample two, and so on. Each sample is simply a block of compressed bytes: no timing, no structure, just encoded data. The movie file itself comes later.

Container architecture

MP4, MOV, and the wider ISO Base Media File Format are not codecs. They are structured containers built from a hierarchy of boxes, sometimes called atoms, that organise raw encoded data into a navigable, time-aware system. Two are foundational:

The sample tables answer the critical questions every player needs:

• Where does each sample start in the data stream?
• How large is each sample in bytes?
• How long should each sample be displayed?
• Which samples are keyframes?

Several tables work together to provide this map. One records the size of each sample, another records the byte offset of each sample inside mdat, another defines how long each sample lasts in time, and another flags random access frames. Together, these tables define how encoded samples are located, timed, and presented.

The Clock Model

The timescale clock system

MP4 does not store time in frames per second; instead, it uses a clock system based on time units called a timescale. The media declares how many ticks equal one second.

Example — 25 fps at timescale 25,000

Each video sample is then assigned a duration in those units. At 25 frames per second, there are 25 samples per second, so each sample must last:

The timing table simply records that each sample has a duration of 1,000 ticks. After 25 samples, the accumulated duration reaches 25,000 ticks — exactly one second of playback.

Example — 25 fps at timescale 90,000

Many professional systems use a timescale of 90,000. The math works the same way.

Each frame lasts 3,600 time units. Accumulate 25 of them and you have one second.

Standard Video

Frame rate to sample rate

In standard video, one sample equals one frame:

Audio works differently, but video is almost always one compressed sample per frame.

The encoding pipeline

Putting the whole system together, the pipeline looks like this:

1. Raw frames go into the encoder.
2. The encoder compresses each frame into a sample.
3. The muxer writes every sample sequentially into mdat.
4. Simultaneously, it builds the sample tables inside moov — recording for each sample its byte position, byte size, duration in time units, and whether it is a keyframe or B-frame.
5. Once complete, the MP4 file becomes a fully indexed, time-aware assembly of media.

Timing Internals

Grouped runs, decode & presentation time

Grouped runs

Timing inside the file is often stored in grouped runs. Instead of listing every frame individually, the timing table might specify eight samples, each lasting 3,600 ticks. In a 90,000 timescale system, that equals:

Again, the clock emerges purely from accumulated durations.

Decoding time vs presentation time

The format includes two related timing concepts: decoding time and presentation time. Because modern codecs reorder frames internally, the order frames are decoded is not always the order they are displayed. The container handles this using an additional composition offset table. But even here, everything is still expressed as time deltas in ticks. The same clock model applies.

Architecture at a Glance

The components, and their role in ION

ION's Orchestration Capability

The static sample table, made programmable

ION treats the static sample table not as a fixed output but as a programmable reference space.

Rather than treating the MP4 container as the final authority on structure, ION virtualises encoded video samples so their timing, ordering, and inclusion can be dynamically controlled by an orchestration engine rather than a fixed sample table generated at encode time.

Each compressed frame or segment becomes independently addressable. The orchestration layer computes a personalised assembly graph that maps virtualised references to underlying encoded media across one or more source files, resolving SMPTE timecodes (H:M:S:F) to sample locations, managing the container structure, format, sample mapping, and reference file locations simultaneously.

The virtualisation principle

ION does for video what virtual memory did for compute and what object storage did for cloud: it introduces an abstraction layer that separates the logical structure from the physical storage. Rendered media becomes addressable, composable, and dynamically orchestrated by intelligent systems.

Four decoupled layers

The architectural consequence of ION's virtualisation is that four previously bound operations become independently programmable:

AI-Native Implications

Video as a real-time computable medium

For AI platforms, ION's architecture creates a new primitive: video as an orchestratable, real-time computable medium. Intelligent systems do not generate new video files. They generate assembly instructions.

AI models can select, sequence, and time video components based on user context, intent, behavioural signals, or inference outputs. The orchestration layer resolves these instructions into a valid virtual assembly graph referencing existing encoded media. Progressive delivery of the assembled stream begins immediately.

This architecture unlocks capabilities that are not practically achievable with traditional rendering models:

• Scalable personalisation at infrastructure cost profiles, with no per-variation encode cost
• Contextual highlights, summaries, and adaptive narratives assembled in real-time
• AI-driven content composition across distributed source media without duplication
• Continuous adaptive video experiences that respond to evolving inference outputs
• Agent-driven content creation where AI orchestration replaces traditional editorial pipelines

Compatibility & Infrastructure Integration

A programmable layer above existing media

ION's approach remains fully compatible with existing codec ecosystems and streaming infrastructure. Underlying media is standard compressed samples stored in standard containers. What changes is the control plane that governs how those samples are referenced, assembled, and delivered.

Existing CDNs, players, and delivery infrastructure operate without modification. ION sits upstream as the data layer: it produces valid, standards-compliant virtual assembly outputs that downstream infrastructure handles identically to conventionally encoded streams.

For organisations operating at scale across content, AI, media delivery, or personalised digital experiences, this integration profile is critical. ION does not require infrastructure replacement. It adds a programmable assembly layer above existing encoded media stores, extending the capability of the entire downstream stack without disrupting it.

Patent Protection

A foundational granted patent estate

The video virtualisation architecture described in this document is protected by four foundational granted patents, with an additional 2026 patent filing extending protection into the runtime control and governance layer. The foundational patent estate covers the core method of virtualising encoded video samples into an independently addressable reference space, enabling dynamic assembly without re-encoding.

In 2026, ION filed a further patent application in Australia and the United States, extending this protection into the control layer of Virtual Video. The filing covers token-governed runtime resolution, including authorisation, licensing, territorial conditions, consent parameters, transaction rules, and device or session validation at the moment of assembly.

This extends ION's protection beyond video virtualisation and dynamic assembly into the governance and commercialisation layer required for AI-native and agentic media environments.

Conclusion

A virtualisation layer for video

ISO Base Media is not just a file format. It is a time-indexed assembly framework for compressed media. The separation between the mdat warehouse and the moov assembly map is a foundational architectural design choice. ION extends this design by making the assembly map programmable, dynamic, and AI-driven.

For any organisation building AI systems, cloud infrastructure, or intelligent media workflows at scale, ION represents a foundational infrastructure primitive: the layer that makes rendered video programmable by intelligent systems.